Machine to machine traffic management methods and systems

ABSTRACT

A method and system for managing M2M traffic in a network is provided. The M2M device sends a message that includes a machine identity for the M2M device. A query is submitted to a database that correlates the machine identity with a QoS parameter or a priority. The message is assigned to one of a plurality of input queues based on the assigned QoS parameter or priority. Each input queue is associated with a delay period so that the message is held in the queue for a period less than the delay period.

BACKGROUND OF THE INVENTION

The subject matter disclosed herein generally relates to communicationsinvolving wireless devices and more particularly to methods and systemsfor managing differentiated wireless device traffic such as machine tomachine (M2M) traffic to manage network performance.

The rapid development of telecommunications technologies has allowedproviders of a wide range of services to manage and control devicesremotely. M2M devices communicate with other devices and/or systems ofsimilar capabilities. M2M devices have applications in a variety ofservice areas including security, tracking and tracing, payment, health,remote maintenance and control, metering, and consumer devices. Examplesof M2M type devices include temperature sensors, water meters, electricmeters, gas meters, automotive navigation aids, emergency notification,digital billboards, or the like. Typically, an M2M device acquiresinformation (e.g., temperature, utility usage, documents, etc.) andprovides the information to another device via a network. Because of thelarge number of potential applications, M2M is expanding at anunprecedented pace, and it is forecasted that through exponential growththere will be 50 billion devices by 2020. Due to the increasing numberof M2M devices entering the marketplace and the resulting traffic, it islikely that network congestion may occur.

A typical cellular network includes a radio access network and a corenetwork. The key core network components are a database of devicelocations and security keys and the “front end workers” that are thecomputers/servers in front of it to allow many transactions per second.The core network is designed for the rapid response needed for makingsynchronous voice calls. Much of the cost of network elements like theHome Location Register/Home Subscriber Service (HLR/HSS) is driven bythe low latency required to connect to the network and the networklocating the other party. This all happens within milliseconds. Thelower the latency needs, the more front end worker resources that mustbe applied.

Currently all M2M traffic is treated equally, which results in networkcongestion when massive numbers of machines are attempting tocommunicate with each other simultaneously. Consequently, today there isa single “quality” level at the core network. However, not all M2Mcommunications require the same Quality of Service (QoS) as synchronousvoice communications, in that M2M communications may have a higherlatency tolerance than synchronous voice communications.

Services like voice calls require high QoS via low latency. Video hashigh data throughput requirements. These needs have driven thedevelopment of network air interface bearers and the ability to assignthe resources to ensure service experiences. The maturity of QoS isaround allocation of the scarce radio access network resources of whichare primarily spectrum. With M2M traffic there is often a high tolerancefor latency to transmit very small amounts of data. However, the macrocellular network is dimensioned to be able to support high QoS serviceslike voice and video. Even though M2M devices may use very littlethroughput meaning they do not consume much of the scarcest resource ofspectrum, overall costs to operate an M2M network are high, partlydriven by the bottleneck (and cost) moving into the core network.Therefore, there is a need for methods and systems to manage M2M trafficin a way that reduces network congestion. There is a need for a methodand system to manage M2M traffic based on the QoS requirements andlatency needs of M2M devices.

BRIEF DESCRIPTION OF THE INVENTION

The disclosure provides a solution to the problem of network congestionresulting from M2M traffic. This solution proposes a good/better/bestapproach for M2M QoS that relies on latency tolerance at the homesubscriber server. For devices that could tolerate several secondsdelay, messages could be routed to a system with fewer front end workerresources. For those that needed higher quality, they could go to asystem with more front end worker resources.

In accordance with one exemplary non-limiting embodiment, the inventionrelates to a method for managing M2M traffic that includes the steps ofreceiving a message request from a first device. The message requestincludes a machine identity for the first device. A query is submittedto a database that correlates the machine identity with a QoS parameter.The method then determines the QoS parameter associated with the firstdevice based on the machine identity and assigns an assigned priority tothe message. The assigned priority is selected from at least a firstpriority and a second lower priority based on the first QoS parameter.The method further includes the step of assigning the message to anassigned input queue based on the assigned priority. The assigned inputqueue is selected from among a first input queue having a firstassociated delay into which a set of first priority messages areassigned and a second input queue having a second associated delay intowhich a set of second priority messages are assigned.

In another embodiment, a system is provided having a computer, a storagemedium, and a node that receives a request to transmit a message from afirst device, the message request including a machine identity for thefirst device. The system also includes a subsystem that determines themachine identity for the first device. A database is stored in thestorage medium. The database stores information associating the machineidentity with a QoS parameter. A subsystem that determines the QoSparameters for the first device based on the machine identity is alsoincluded. The system also includes a subsystem that assigns an assignedpriority for the message based on the QoS parameter where the assignedpriority is selected from among a first priority and a second lowerpriority. The system also includes a subsystem that assigns the messageto an assigned input queue based on the assigned priority. The assignedinput queue is selected from among a first input queue having a firstassociated delay into which a first set of assigned messages having thefirst priority are assigned and a second input queue having a secondassociated delay into which a second set of assigned messages having thesecond lower priority are assigned.

In another embodiment, a method includes receiving a request to send amessage from a first machine to a second machine. The method includesthe step of receiving a first QoS identifier from the first machine;wherein the first QoS identifier includes a priority and a QoSparameter. The method also includes the step of assigning the message toan assigned input queue. The assigned input queue is selected from atleast a first input queue and a second input queue based on the priorityof the first QoS identifier. The first input queue has a firstassociated delay into which a set of first priority messages areassigned and the second input queue has a second associated delay intowhich a set of second priority messages are assigned.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features and advantages of the present invention will be apparentfrom the following more detailed description of the preferredembodiment, taken in conjunction with the accompanying drawings whichillustrate, by way of example, the principles of certain aspects of theinvention.

FIG. 1 is a schematic of some elements of a traffic management system inaccordance with one embodiment of the invention.

FIG. 2 illustrates a non-limiting exemplary method of implementing oneor more disclosed embodiments.

FIG. 3 illustrates a non-limiting exemplary alternate method ofimplementing one or more disclosed embodiments.

FIG. 4 is a schematic diagram of a wireless device that may be used inconnection with an embodiment.

FIG. 5 is a block diagram of an exemplary processor which may beemployed in an embodiment.

FIG. 6 is an overall block diagram of an exemplary packet-based mobilecellular network environment, such as a GPRS network, in which thepresent subject matter may be implemented.

FIG. 7 illustrates a non-limiting, exemplary architecture of a typicalGPRS network.

FIG. 8 illustrates a non-limiting alternate block diagram of anexemplary GSM/GPRS/IP multimedia network architecture in which thepresent subject matter may be implemented.

FIG. 9 illustrates a non-limiting PLMN block diagram view of anexemplary architecture in which one or more disclosed embodiments may beimplemented.

DETAILED DESCRIPTION OF THE INVENTION

Illustrated in FIG. 1 is an illustrative embodiment of an M2M trafficmanagement system 100 for use with a network 101, such as, for example acellular network. The M2M traffic management system 100 may beimplemented in a variety of netwrok types such as WiFi, BlueTooth,wireline, cellular, etc. In the case of a cellular network, network 101may be a cellular network operating under a Global System for MobileCommunication (GSM) standard, a Long-Term Evolution (LTE) standard, orin a Universal Mobile Telecommunications System (UMTS) standard.Although only three of the commonly used standards are described hereinit would be apparent to one of ordinary skill in the art that the M2Mtraffic management system 100 may also be used with cellular networksoperating on new standards such as the contemplated 5G standards. TheM2M traffic management system 100 may include radio access network (RAN)105 that is the part of the network responsible for having physicalradio connectivity for users. The RAN 105 may include a plurality ofbase stations (BTS) 110 (only one is shown) (Node B in UMTS terminology,base transceiver station in GSM terminology). The primary task of BTS110 is to handle physical layer functions and perform basic radioresource management operations. Also included in the M2M trafficmanagement system 100 may be a Base Station Controller (BSC) 115 (or ARadio Network Controller (RNC) in the case of UMTS network). In LTE, thecontroller and base station functions are combined in an Enhanced Node B(eNodeB). The BSC 115 allocates radio channels and controls handoversfrom BTS 110. BSC 115 acts as a concentrator where many different lowcapacity connections to BTSs having relatively low utilization level arereduced to a smaller number of connections towards a mobile switchingcenter (MSC) 130 having a higher utilization level.

The M2M traffic management system 100 may service a plurality of mobilestations (MS 120, MS 121 and MS 122) (or User Equipment (UE) in UMTS andLTE terminology). MS 120 may be a mobile telephone, a personal digitalassistant, a computer, a tablet, or an M2M device with GSM (or UMTS, orLTE) capability. Each MS, e.g. MS 120 has associated with it a machineidentity. For example, the MS 120 has an International Mobile StationEquipment identity or IMEI. The IMEI is a number that identifies the MS120 and is used by a GSM network to identify valid devices. Anothermachine identity may be the MSISDN that is a number uniquely identifyinga subscription in a GSM or UMTS mobile network. Yet another machineidentity may be a serial number of the MS 120. The M2M trafficmanagement system 100 may include an arbitrary number of certainentities (e.g., MS 120, BTS 110, BSC 115) shown in FIG. 1. Moreover, forthe sake of simplicity, FIG. 1 omits certain entities (e.g., operationsand maintenance center, and business systems).

The M2M traffic management system 100 may also include a core network125. The core network 125 performs switching for calls involving forexample a GSM network. The main component of the core network 125 is themobile switching center (MSC) 130 which operates in conjunction with ahome location register (HLR) 135. The HLR 135 is a database that storesinformation about subscribers in the M2M traffic management system 100.The MSC 130 is a server mostly associated with communications switchingfunctions, such as registration, authentication, location updating, callset-up, release, and routing. However, it may also provide otherfunctions such as routing SMS messages, conference calls, fax, andservice billing as well as interfacing with other networks, such as thepublic switched telephone network (PSTN). The MSC 130 is structured sothat base stations such as BTS 110 connect to it, while it connects tothe public switched telephone network (PSTN). All forms ofcommunication, including M2M communications travel through the MSC 130.

As illustrated in FIG. 1 the core network 125 may include, in additionto MSC 130, a Service Control Point (SCP) 140, a gateway MSC 145, aservice GPRS support node (SGSN 150), a Home Location AuthenticationCenter (AuC) 155, a Domain Name Server (DNS) 160, and a Gateway GPRSsupport node (GGSN) 165. M2M traffic management system 100 may alsocomprise a host of various networks and other network elements.

Associated with the MSC 130 may be an M2M traffic application 170 and anM2M database 175. M2M database 175 associates a QoS and a priority withthe machine identity of an MS 120. The M2M traffic application 170determines the QoS and priority associated with the MS 120 and assigns apriority to a message. The M2M database 175 and the M2M trafficapplication 170 may be located within or outside of the core network125. In one embodiment the M2M traffic application 170 and the M2Mdatabase 175 may be located outside the core network to avoidbottlenecks at the MSC 130.

The M2M traffic management system 100 may be connected to one or moreexternal networks such as networks 141, and 142. Networks 141 and 142may be connected to a mobile station 143 such as a personal digitalassistant, a computer, a tablet computer, or an M2M device. The mobilestation 143 may be connected to networks 141 and 142 using a variety oftechnologies such as Wi-Fi, Bluetooth, ANT, ZigBee, IEEE802.15.4, amongothers. The M2M traffic management system 100 in this embodiment wouldbe used to manage traffic between the mobile station 143 connected tonetworks 141 and 142 and devices connected to a cellular network. Inthis embodiment the M2M traffic management system 100 serves as agateway for M2M communications using different protocols and airinterfaces.

The M2M traffic management system 100 may also include a plurality ofinput queues (storage structures in memory), for example, a first inputqueue 180, a second input queue 185 and a third input queue 190. Theinput queues are used to store messages for a predetermined period oftime. First input queue 180, second input queue 185 and third inputqueue 190 may be located at an access node in the RAN 105. These queuescould be sub-system partitions. First input queue 180, second inputqueue 185 and third input queue 190 store the messages that need to betransmitted eventually. For example, a first message in the first inputqueue (for messages with higher priority) 180 may be transmitted beforea second message in the second input queue 185 (for messages with lowerpriority) even though the first message was received after the secondmessage. Although three input queues are illustrated in the example ofFIG. 1 it will be understood by one of ordinary skill in the art thatany number of queues may be employed. Alternately, messages in thesecond input queue 185 and the third input queue 190 may be routed to asystem with fewer front end worker resources or to a smaller corenetwork 125.

Associated with each input queue are a priority level and apredetermined delay. For example first input queue 180 may be associatedwith a low priority and has a long delay (of between, for example,greater than 400 ms) such that an M2M message will be postponed and notdelivered immediately. Second input queue 185 may be associated with amedium priority and may have a medium delay (of between, for example,100 ms and 400 ms) such that an M2M message will be postponed brieflyand then delivered. Third input queue 190 may have high priority and mayhave a short delay (for example between 0 ms and 150 ms) such that theM2M message will not be postponed significantly and will be deliveredalmost immediately.

In operation, an MS 120 may be a machine that seeks to communicate witha second machine MS 121. MS 120 would send a machine identity to the RAN105 which communicates the first machine identity to the core network125. In the core network 125 there is an M2M database 175 thatassociates the machine identity with one or more QoS parameters.Although the M2M database 175 is described in this embodiment as beinglocated in the core network 125, it would be apparent to one of ordinaryskill in the art that the M2M database 175 may be located at anylocation in communication with the RAN 105.

The M2M database 175 may also assign each machine identity with apriority. The M2M traffic application 170 will assign a priority to themessage based on the QoS parameters for the MS 120. The MSC 130 in thecore network 125 receives the priority from the M2M traffic application170 and communicates the priority to the BSC 115 (or an RNC or aneNodeB). BSC 115 will assign the message to an input queue based on thepriority. Associated with each input queue is a delay that delaystransmission of the message for a predetermined period of time.

The assignment of a message to a particular input queue depends on howdelay sensitive the traffic is—conversational and streaming traffic aremore delay sensitive, interactive and background are less so. Because ofthe less restrictive delay requirements when compared to conversationaland streaming classes, both interactive and background classes providebetter error rates. Conversational voice and video and interactive gamesare delay sensitive and have a delay requirement of much less than 1second. Voice messaging, e commerce and web browsing applications areless delay sensitive and have a delay requirement of approximately 1second. Streaming audio and video have delay requirements of less than10 seconds while fax and email arrival notification may have delayrequirements of greater than 10 seconds.

For example, a first machine with high latency such as an electric metermay need to communicate with a second machine through a cellularnetwork. The cellular network may be transmitting a large number ofdifferent types of messages such as for example conversational andstreaming messages, voice messaging messages, streaming audio and videomessages, and fax and email messages. Conversational and streamingmessages may be assigned a high priority and assigned to a first inputqueue 180 having a delay of for example between 0 ms and 150 ms.Messages from the first machine may be assigned an intermediate priorityand assigned to a second input queue having a delay of for examplebetween 100 ms and 400 ms. Messages from the first machine may beassigned a low priority and assigned to a third input queue 190 having athird delay of for example greater than 400 ms. The message from theelectric meter will be held in the third input queue for the period ofthe third delay or until there is sufficient capacity to send themessage and the messages in the first input queue 180 and the secondinput queue 185 have been sent. Alternately, messages from the secondinput queue may be sent to a to a system with fewer front end workerresources, or a core networks with spare capacity. Input queues may bemanaged with a scheduling algorithm such as first in first out (FIFO) orany other suitable scheduling algorithm.

Illustrated in FIG. 2 is an embodiment of a method 200 for managing M2Mtraffic in a cellular network.

In step 205, the method 200 receives a request to transmit a messagebetween a source machine and a destination machine.

In step 210, the method 200 acquires a machine identity for the sourcemachine and the destination machine.

In step 215, the method 200 submits a query to the database, the queryincluding the source machine identity and destination machine identity.

In step 220, the method 200 determines a priority for the source machineand destination machine based on the source machine identity.

In step 225, the method 200 forwards the priority information to anetwork access point (e.g. BSC 115 or eNodeB).

In step 230, the method 200 instructs the BSC 115 to assign the messageto an input queue selected from among at least a first input queue formessages with a high priority and a second input queue for messages witha lower priority based on the priority of the source machine. Messagesin the first input queue may have a short delay before being transmittedwhile messages in the second input queue may have a longer delay beforebeing transmitted.

In step 235, the method 200 places the message in the assigned inputqueue.

In step 240, the method 200 instructs the transmission of the messageafter transmitting messages from queues having higher priority.Alternately, the transmission of the message may be routed to a systemwith fewer front end worker resources.

For example, in the case where the source machine is a meter, and thedestination machine is a server, the message may be assigned a lowpriority and routed through a third input queue, where the rules for theinput queue are to hold the message up to a relatively long (>2 seconds)predetermined period of time (delay) or until messages in the firstinput queue and second input queue have been transmitted and there issufficient capacity available to send the message. In a case where thesource machine is a game console the message may be assigned a highpriority and routed through the first input queue, where the rules forthe input queue are to hold the message for a relatively short period oftime (<150 ms) (delay) and the messages may be sent on a first in firstout basis. If the residence time of a message in a queue exceed thedelay associated with the queue then the message may be dropped.

Illustrated in FIG. 3 is another embodiment of a method 250 for machineto machine traffic management. In this embodiment each machine isassociated with a priority parameter which is in turn associated with aQoS requirement for the machine. For example, a machine with a lowlatency tolerance may be provided with a high priority parameter and amachine with a high latency tolerance may be provided with a lowpriority parameter.

In step 255 the method 200 receives a request to send a message from afirst machine to a second machine.

In step 260 the method 200 receives the priority parameter from thefirst machine.

In step 65 the method 200 assigns the first machine to a first selectedinput queue from a plurality of input queues based on the priorityparameter of the first machine. Each of the plurality of input queues isassociated with a priority and a delay. For example a first queue may beassociated with a high priority and has a short delay (of between, forexample, 0 ms and 150 ms) such that an M2M message will be deliveredimmediately. The messages in a queue may be delivered on a FIFO basis. Asecond queue may be associated with a medium priority and may have amedium delay (of between, for example, 100 ms and 400 ms) such that anM2M message will be postponed briefly and then delivered. The messagesin the second queue may be delivered on a FIFO basis. A third inputqueue may be associated with a low priority and may have a long delay(for example between greater than 400 ms) such that the M2M message willbe postponed for at most the period of the long delay and will bedelivered after all messages in the first input queue and the secondinput queue have been delivered. Alternately, the messages in the secondand third input queues may be delivered to alternate system with fewerfront end worker resources.

In step 275 the method 200 transmits the message from the selected inputqueue.

Various scheduling policies can be used at queuing nodes. In FIFO,messages are served one at a time and the message that has been waitingthe longest is served first. The M2M traffic management system 100 hasthe advantage that all the M2M traffic is not treated “equal.” Itprovides the ability to leverage QoS and/or priority handling to managemassive M2M traffic. The result is that the cellular network will notbecome significantly overloaded when massive numbers of M2M devicescommunicate with each other.

FIG. 4 illustrates an example wireless device 1010 that may be used inconnection with an embodiment. References will also be made to otherfigures of the present disclosure as appropriate. For example, mobiledevices (e.g. MS 120 and 121) may be wireless devices of the typedescribed in regard to FIG. 4, and may have some, all, or none of thecomponents and modules described in regard to FIG. 4. It will beappreciated that the components and modules of wireless device 1010illustrated in FIG. 4 are illustrative, and that any number and type ofcomponents and/or modules may be present in wireless device 1010. Inaddition, the functions performed by any or all of the components andmodules illustrated in FIG. 4 may be performed by any number of physicalcomponents. Thus, it is possible that in some embodiments thefunctionality of more than one component and/or module illustrated inFIG. 4 may be performed by any number or types of hardware and/orsoftware.

Processor 1021 may be any type of circuitry that performs operations onbehalf of wireless device 1010. Such circuitry may include circuitry andother components that enable processor 1021 to perform any of thefunctions and methods described herein. Such circuitry and othercomponents may also enable processor 1021 to communicate and/or interactwith other devices and components, for example any other component ofdevice of wireless device 1010, in such a manner as to enable processor118 and such other devices and/or components to perform any of thedisclosed functions and methods. In one embodiment, processor 1021executes software (i.e., computer readable instructions stored in acomputer readable medium) that may include functionality related tointelligent peer-to-peer management, for example. User interface module1022 may be any type or combination of hardware and/or software thatenables a user to operate and interact with wireless device 1010, and,in one embodiment, to interact with a system or software enabling theuser to place, request, and/or receive calls, text communications of anytype, voicemail, voicemail notifications, voicemail content and/or data,and/or a system or software enabling the user to view, modify, or deleterelated software objects. For example, user interface module 1022 mayinclude a display, physical and/or “soft” keys, voice recognitionsoftware, a microphone, a speaker and the like. Wireless communicationmodule 1023 may be any type of transmitter, receiver, or transceiverincluding hardware or a combination of hardware and/software thatenables wireless device 1010 to communicate with cellular networkequipment. Memory 1024 enables wireless device 1010 to storeinformation, such as APNs, MNCs, MCCs, text communications content andassociated data, multimedia content, software to efficiently processradio resource requests and service requests, and radio resource requestprocessing preferences and configurations. Memory 1024 may take anyform, such as internal random access memory (RAM), an SD card, a microSDcard and the like. Power supply 1025 may be a battery or other type ofpower input (e.g., a charging cable that is connected to an electricaloutlet, etc.) that is capable of powering wireless device 1010. SIM 1026may be any type Subscriber Identity Module and may be configured on aremovable or non-removable SIM card that allows wireless device 1010 tostore data on SIM 1026.

FIG. 5 is a block diagram of an example processor 1158 which may beemployed in any of the embodiments described herein, including as one ormore components of MS 120 and 121, as one or more components of networkequipment such as MMEs, and HSSs, and/or CMS, or any other component ofthe outside networks 141 and 142, and/or any related equipment, and/oras one or more components of any third party system or subsystem thatmay implement any portion of the subject matter described herein. It isemphasized that the block diagram depicted in FIG. 5 is exemplary andnot intended to imply a specific implementation. Thus, the processor1158 can be implemented in a single processor or multiple processors.Multiple processors can be distributed or centrally located. Multipleprocessors can communicate wirelessly, via hard wire, or a combinationthereof. Processor 1158 may include circuitry and other components thatenable processor 1158 to perform any of the functions and methodsdescribed herein. Such circuitry and other components may also enableprocessor 1158 to communicate and/or interact with other devices andcomponents, for example any other component of any device disclosedherein or any other device, in such a manner as to enable processor 1158and such other devices and/or components to perform any of the disclosedfunctions and methods.

As depicted in FIG. 5, the processor 1158 comprises a processing portion1160, a memory portion 1162, and an input/output portion 1164. Theprocessing portion 1160, memory portion 1162, and input/output portion1164 are coupled together (coupling not shown in FIG. 5) to allowcommunications between these portions. The input/output portion 1164 iscapable of providing and/or receiving components, commands, and/orinstructions, utilized to, for example, request and receive APNs, MNCs,and/or MCCs, establish and terminate communications sessions, transmitand receive service requests and data access request data and responses,transmit, receive, store and process text, data, and voicecommunications, execute software that efficiently processes radioresource requests, receive and store service requests and radio resourcerequests, radio resource request processing preferences andconfigurations, and/or perform any other function described herein.

The processor 1158 may be implemented as a client processor and/or aserver processor. In a basic configuration, the processor 1158 mayinclude at least one processing portion 1160 and memory portion 1162.The memory portion 1162 can store any information utilized inconjunction with establishing, transmitting, receiving, and/orprocessing text, data, and/or voice communications,communications-related data and/or content, voice calls, othertelephonic communications, etc. For example, the memory portion iscapable of storing APNs, MNCs, MCCs, service requests, radio resourcerequests, QoS and/or APN parameters, software for intelligent peer-topeer communications, text and data communications, calls, voicemail,multimedia content, visual voicemail applications, etc. Depending uponthe exact configuration and type of processor, the memory portion 1162can be volatile (such as RAM) 1166, non-volatile (such as ROM, flashmemory, etc.) 1168, or a combination thereof. The processor 1158 canhave additional features/functionality. For example, the processor 1158may include additional storage (removable storage 1170 and/ornon-removable storage 1172) including, but not limited to, magnetic oroptical disks, tape, flash, smart cards or a combination thereof.Computer storage media, such as memory and storage elements 1162, 1170,1172, 1166, and 1168, may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Computer storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory, smart cards, or any other medium that can be used tostore the desired information and that can be accessed by the processor1158. Any such computer storage media may be part of the processor 1158.It is to be understood that a computer storage medium, as describedherein, is not to be construed as a transient signal.

The processor 1158 may also contain the communications connection(s)1180 that allow the processor 1158 to communicate with other devices,for example through a radio access network (RAN). Communicationsconnection(s) 1180 is an example of communication media. Communicationmedia typically embody computer-readable instructions, data structures,program modules or other data in a modulated data signal such as acarrier wave or other transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection as might be used with a land line telephone, andwireless media such as acoustic, RF, infrared, cellular, and otherwireless media. The term computer-readable media as used herein includesboth storage media and communication media. It is to be understood,however, that a computer-readable storage medium, as described herein,is not to be construed as a transient signal. The processor 1158 alsocan have input device(s) 1176 such as keyboard, keypad, mouse, pen,voice input device, touch input device, etc. Output device(s) 1174 suchas a display, speakers, printer, etc. also can be included.

A RAN as described herein may comprise any telephony radio network, orany other type of communications network, wireline or wireless, or anycombination thereof. The following description sets forth some exemplarytelephony radio networks, such as the global system for mobilecommunications (GSM), and non-limiting operating environments. Thebelow-described operating environments should be considerednon-exhaustive, however, and thus the below-described networkarchitectures merely show how intelligent peer-to-peer management may beimplemented with stationary and non-stationary network structures andarchitectures in order to do intelligent peer-to-peer management. It canbe appreciated, however, that intelligent peer-to-peer management asdescribed herein may be incorporated with existing and/or futurealternative architectures for communication networks as well.

The GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. The GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (GPRS), which is anextension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein alsomay be extended to 3G services, such as Universal Mobile TelephoneSystem (UMTS), Frequency Division Duplexing (FDD) and Time DivisionDuplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1×Evolution Data Optimized (EVDO), Code Division Multiple Access-2000(cdma2000 3×), Time Division Synchronous Code Division Multiple Access(TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), EnhancedData GSM Environment (EDGE), International MobileTelecommunications-2000 (IMT-2000), Digital Enhanced CordlessTelecommunications (DECT), 4G Services such as Long Term Evolution(LTE), etc., as well as to other network services that become availablein time. In this regard, intelligent peer-to-peer management may beapplied independently of the method of data transport.

Embodiments disclosed herein may allow for communications single andnetwork service provider networks. P2P notification messages may be sentacross the network(s) from a P2P end device to another P2P end device toquery communication availability of a P2P end device. Communicationavailability may include uptime, bandwidth resources of for uplink anddownlink communication, and the like.

FIG. 6 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichintelligent peer-to-peer management systems and methods such as thosedescribed herein may be practiced. In an example configuration, any RANas described herein may be encompassed by or interact with the networkenvironment depicted in FIG. 6. Similarly, MS 120 and 121 maycommunicate or interact with a network environment such as that depictedin FIG. 6. In such an environment, there may be a plurality of BaseStation Subsystems (BSS) 900 (only one is shown), each of whichcomprises a Base Station Controller (BSC) 902 serving a plurality ofBase Transceiver Stations (BTS) such as BTSs 904, 906, and 908. BTSs904, 906, 908, etc. are the access points where users of packet-basedmobile devices (e.g., MS 120, 121 and 122) become connected to thecellular network. In exemplary fashion, the packet traffic originatingfrom user devices (e.g., MS 120 and 121) may be transported via anover-the-air interface to a BTS 908, and from the BTS 908 to the BSC902. Base station subsystems, such as BSS 900, may be a part of internalframe relay network 910 that can include Service GPRS Support Nodes(SGSN) such as SGSN 912 and 914. Each SGSN may be connected to aninternal packet network 920 through which a SGSN 912, 914, etc. mayroute data packets to and from a plurality of gateway GPRS support nodes(GGSN) 922, 924, 926, etc. As illustrated, SGSN 914 and GGSNs 922, 924,and 926 may be part of internal packet network 920. Gateway GPRS servingnodes 922, 924 and 926 may provide an interface to external InternetProtocol (IP) networks, such as Public Land Mobile Network (PLMN) 950,corporate intranets 940, or Fixed-End System (FES) or the publicInternet 930. As illustrated, subscriber corporate network 940 may beconnected to GGSN 924 via firewall 932, and PLMN 950 may be connected toGGSN 924 via border gateway router 934. The Remote AuthenticationDial-In User Service (RADIUS) server 942 may be used for callerauthentication when a user of a mobile cellular device calls corporatenetwork 940.

Generally, there can be four different cell sizes in a GSM network,referred to as macro, micro, pico, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells may beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells may betypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells may be used mainly indoors.On the other hand, umbrella cells may be used to cover shadowed regionsof smaller cells and fill in gaps in coverage between those cells.

FIG. 7 illustrates an architecture of a typical GPRS network segmentedinto four groups: users 1050, radio access network 1060, core network1070, and interconnect network 1080. Users 1050 may comprise a pluralityof end users (though only mobile subscriber 1055 is shown in FIG. 7). Inan example embodiment, the device depicted as mobile subscriber 1055 maycomprise any of MS 120 and 121. Radio access network 1060 comprises aplurality of base station subsystems such as BSSs 1062, which includeBTSs 1064 and BSCs 1066. Core network 1070 comprises a host of variousnetwork elements. As illustrated here, core network 1070 may compriseMobile Switching Center (MSC) 1071, Service Control Point (SCP) 1072,gateway MSC 1073, SGSN 1076, Home Location Register (HLR) 1074,Authentication Center (AuC) 1075, Domain Name Server (DNS) 1077, andGGSN 1078. Interconnect network 1080 may also comprise a host of variousnetworks and other network elements. As illustrated in FIG. 7,interconnect network 1080 comprises Public Switched Telephone Network(PSTN) 1082, Fixed-End System (FES) or Internet 1084, firewall 1088, andCorporate Network 1089.

A mobile switching center may be connected to a large number of basestation controllers. At MSC 1071, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (PSTN) 1082 through Gateway MSC (GMSC)1073, and/or data may be sent to SGSN 1076 that may send the datatraffic to GGSN 1078 for further forwarding.

When MSC 1071 receives call traffic, for example, from BSC 1066, it maysend a query to a database hosted by SCP 1072. The SCP 1072 may processthe request and may issue a response to MSC 1071 so that it may continuecall processing as appropriate.

The HLR 1074 may be a centralized database for users to register to theGPRS network. In some embodiments, HLR 1074 may be a device such asHSSs. HLR 1074 may store static information about the subscribers suchas the International Mobile Subscriber Identity (IMSI), APN profiles asdescribed herein, subscribed services, and a key for authenticating thesubscriber. HLR 1074 may also store dynamic subscriber information suchas dynamic APN profiles and the current location of the mobilesubscriber. HLR 1074 may also serve to intercept and determine thevalidity of destination numbers in messages sent from a device, such asmobile subscriber 1055, as described herein. Associated with HLR 1074may be AuC 1075. AuC 1075 may be a database that contains the algorithmsfor authenticating subscribers and may include the associated keys forencryption to safeguard the user input for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as MS 120 and 121, used by an end user of a mobile cellularservice or a wireless provider. When a mobile subscriber turns on his orher mobile device, the mobile device may go through an attach process bywhich the mobile device attaches to an SGSN of the GPRS network. In FIG.7, when mobile subscriber 1055 initiates the attach process by turningon the network capabilities of the mobile device, an attach request maybe sent by mobile subscriber 1055 to SGSN 1076. The SGSN 1076 queriesanother SGSN, to which mobile subscriber 1055 was attached before, forthe identity of mobile subscriber 1055. Upon receiving the identity ofmobile subscriber 1055 from the other SGSN, SGSN 1076 may request moreinformation from mobile subscriber 1055. This information may be used toauthenticate mobile subscriber 1055 to SGSN 1076 by HLR 1074. Onceverified, SGSN 1076 sends a location update to HLR 1074 indicating thechange of location to a new SGSN, in this case SGSN 1076. HLR 1074 maynotify the old SGSN, to which mobile subscriber 1055 was attachedbefore, to cancel the location process for mobile subscriber 1055. HLR1074 may then notify SGSN 1076 that the location update has beenperformed. At this time, SGSN 1076 sends an Attach Accept message tomobile subscriber 1055, which in turn sends an Attach Complete messageto SGSN 1076.

After attaching itself to the network, mobile subscriber 1055 may thengo through the authentication process. In the authentication process,SGSN 1076 may send the authentication information to HLR 1074, which maysend information back to SGSN 1076 based on the user profile that waspart of the user's initial setup. The SGSN 1076 may then send a requestfor authentication and ciphering to mobile subscriber 1055. The mobilesubscriber 1055 may use an algorithm to send the user identification(ID) and password to SGSN 1076. The SGSN 1076 may use the same algorithmand compares the result. If a match occurs, SGSN 1076 authenticatesmobile subscriber 1055.

Next, the mobile subscriber 1055 may establish a user session with thedestination network, corporate network 1089, by going through a PacketData Protocol (PDP) activation process. Briefly, in the process, mobilesubscriber 1055 may request access to an Access Point Name (APN), forexample, UPS.com, and SGSN 1076 may receive the activation request frommobile subscriber 1055. SGSN 1076 may then initiate a Domain NameService (DNS) query to learn which GGSN node has access to the UPS.comAPN. The DNS query may be sent to the DNS server within the core network1070, such as DNS 1077, that may be provisioned to map to one or moreGGSN nodes in the core network 1070. Based on the APN, the mapped GGSN1078 may access the requested corporate network 1089. The SGSN 1076 maythen send to GGSN 1078 a Create Packet Data Protocol (PDP) ContextRequest message that contains necessary information. The GGSN 1078 maysend a Create PDP Context Response message to SGSN 1076, which may thensend an Activate PDP Context Accept message to mobile subscriber 1055.

Once activated, data packets of the call made by mobile subscriber 1055may then go through radio access network 1060, core network 1070, andinterconnect network 1080, in a particular fixed-end system, or Internet1084 and firewall 1088, to reach corporate network 1089.

Thus, network elements that can invoke the functionality of intelligentpeer-to-peer management systems and methods such as those describedherein may include, but are not limited to, Gateway GPRS Support Nodetables, Fixed End System router tables, firewall systems, VPN tunnels,and any number of other network elements as required by the particulardigital network.

FIG. 8 illustrates another exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture 1100 in which the systems and methodsfor intelligent peer-to-peer management such as those described hereinmay be incorporated. As illustrated, architecture 1100 of FIG. 8includes a GSM core network 1101, a GPRS network 1130 and an IPmultimedia network 1138. The GSM core network 1101 includes a MobileStation (MS) 1102, at least one Base Transceiver Station (BTS) 1104 anda Base Station Controller (BSC) 1106. The MS 1102 is physical equipmentor Mobile Equipment (ME), such as a mobile telephone or a laptopcomputer (e.g., MS 120 and 121) that is used by mobile subscribers, inone embodiment with a Subscriber identity Module (SIM). The SIM includesan International Mobile Subscriber Identity (IMSI), which is a uniqueidentifier of a subscriber. The SIM may also include APNs. The BTS 1104may be physical equipment, such as a radio tower, that enables a radiointerface to communicate with the MS. Each BTS may serve more than oneMS. The BSC 1106 may manage radio resources, including the BTS. The BSCmay be connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1103.

The GSM core network 1101 may also include a Mobile Switching Center(MSC) 1108, a Gateway Mobile Switching Center (GMSC) 1110, a HomeLocation Register (HLR) 1112, Visitor Location Register (VLR) 1114, anAuthentication Center (AuC) 1118, and an Equipment Identity Register(EIR) 1116. The MSC 1108 may perform a switching function for thenetwork. The MSC may also perform other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1110 may provide a gateway between the GSM network and other networks,such as an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1120. Thus, the GMSC 1110 providesinterworking functionality with external networks.

The HLR 1112 may be a database that may contain administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. Such information may include APNs and APN profiles. The HLR1112 may also contain the current location of each MS. The VLR 1114 maybe a database that contains selected administrative information from theHLR 1112. The VLR may contain information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1112 and the VLR 1114,together with the MSC 1108, may provide the call routing and roamingcapabilities of GSM. The AuC 1116 may provide the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1118 may storesecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1109 allows one-to-one shortmessage service (SMS), or multimedia message service (MMS), messages tobe sent to/from the MS 1102. A Push Proxy Gateway (PPG) 1111 is used to“push” (i.e., send without a synchronous request) content to the MS1102. The PPG 1111 acts as a proxy between wired and cellular networksto facilitate pushing of data to the MS 1102. A Short Message Peer toPeer (SMPP) protocol router 1113 may be provided to convert SMS-basedSMPP messages to cell broadcast messages. SMPP is a protocol forexchanging SMS messages between SMS peer entities such as short messageservice centers. The SMPP protocol is often used to allow third parties,e.g., content suppliers such as news organizations, to submit bulkmessages.

To gain access to GSM services, such as voice, data, short messageservice (SMS), and multimedia message service (MMS), the MS may firstregister with the network to indicate its current location by performinga location update and IMSI attach procedure. MS 1102 may send a locationupdate including its current location information to the MSC/VLR, viaBTS 1104 and BSC 1106. The location information may then be sent to theMS's HLR. The HLR may be updated with the location information receivedfrom the MSC/VLR. The location update may also be performed when the MSmoves to a new location area. Typically, the location update may beperiodically performed to update the database as location updatingevents occur.

GPRS network 1130 may be logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1132, a cell broadcast and a GatewayGPRS support node (GGSN) 1134. The SGSN 1132 may be at the samehierarchical level as the MSC 1108 in the GSM network. The SGSN maycontrol the connection between the GPRS network and the MS 1102. TheSGSN may also keep track of individual MS's locations and securityfunctions and access controls.

Cell Broadcast Center (CBC) 1133 may communicate cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile telephone customers whoare located within a given part of its network coverage area at the timethe message is broadcast.

GGSN 1134 may provide a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1136. That is, the GGSN mayprovide interworking functionality with external networks, and set up alogical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it may be transferred to an external TCP-IPnetwork 1136, such as an X.25 network or the Internet. In order toaccess GPRS services, the MS first attaches itself to the GPRS networkby performing an attach procedure. The MS then activates a packet dataprotocol (PDP) context, thus activating a packet communication sessionbetween the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used inparallel. The MS may operate in one three classes: class A, class B, andclass C. A class A MS may attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS may also supportsimultaneous operation of GPRS services and GSM services. For example,class A mobiles may receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS may attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

GPRS network 1130 may be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkmay be indicated by a parameter in system information messagestransmitted within a cell. The system information messages may direct anMS where to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS may receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS maysuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS may bereceiving data and may not be listening to a paging channel. In a NOM3network, a MS may monitor pages for a circuit switched network whilereceiving data and vice versa.

The IP multimedia network 1138 was introduced with 3GPP Release 5, andmay include IP multimedia subsystem (IMS) 1140 to provide richmultimedia services to end users. A representative set of the networkentities within IMS 1140 are a call/session control function (CSCF), amedia gateway control function (MGCF) 1146, a media gateway (MGW) 1148,and a master subscriber database, called a home subscriber server (HSS)1150. HSS 1150 may be common to GSM core network 1101, GPRS network 1130as well as IP multimedia network 1138.

IP multimedia system 1140 may be built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1143, a proxy CSCF (P-CSCF) 1142, and a serving CSCF (S-CSCF) 1144. TheP-CSCF 1142 is the MS's first point of contact with the IMS 1140. TheP-CSCF 1142 may forward session initiation protocol (SIP) messagesreceived from the MS to an SIP server in a home network (and vice versa)of the MS. The P-CSCF 1142 may also modify an outgoing request accordingto a set of rules defined by the network operator (for example, addressanalysis and potential modification).

I-CSCF 1143 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. I-CSCF 1143 may contact subscriberlocation function (SLF) 1145 to determine which HSS 1150 to use for theparticular subscriber, if multiple HSSs 1150 are present. S-CSCF 1144may perform the session control services for MS 1102. This includesrouting originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 1144 may also decidewhether an application server (AS) 1152 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision may be based on information receivedfrom HSS 1150 (or other sources, such as application server 1152). AS1152 may also communicate to location server 1156 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of MS 1102.

HSS 1150 may contain a subscriber profile and keep track of which corenetwork node is currently handling the subscriber. It may also supportsubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1150, a subscriber location function providesinformation on the HSS 1150 that contains the profile of a givensubscriber.

MGCF 1146 may provide interworking functionality between SIP sessioncontrol signaling from the IMS 1140 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown.) It may also control themedia gateway (MGW) 1148 that provides user-plane interworkingfunctionality (e.g., converting between AMR- and PCM-coded voice.) MGW1148 may also communicate with other IP multimedia networks 1154.

Push to Talk over Cellular (PoC) capable mobile telephones may registerwith the cellular network when the telephones are in a predefined area(e.g., job site, etc.) When the mobile telephones leave the area, theymay register with the network in their new location as being outside thepredefined area. This registration, however, does not indicate theactual physical location of the mobile telephones outside thepre-defined area.

FIG. 9 illustrates a PLMN block diagram view of an exemplaryarchitecture in which initiation of a call to an emergency call centermay be incorporated. Mobile Station (MS) 1301 is the physical equipmentused by the PLMN subscriber. In one illustrative embodiment,communications device 40 may serve as Mobile Station 1301. MobileStation 1301 may be one of, but not limited to, a cellular telephone, acellular telephone in combination with another electronic device or anyother wireless mobile communication device.

Mobile Station 1301 may communicate wirelessly with Base Station System(BSS) 1310. BSS 1310 contains a Base Station Controller (BSC) 1311 and aBase Transceiver Station (BTS) 1312. BSS 1310 may include a single BSC1311/BTS 1312 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1310 is responsible for communicating withMobile Station 1301 and may support one or more cells. BSS 1310 isresponsible for handling cellular traffic and signaling between MobileStation 1301 and Core Network 1340. Typically, BSS 1310 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1301 may communicate wirelessly with RadioNetwork System (RNS) 1320. RNS 1320 contains a Radio Network Controller(RNC) 1321 and one or more Node(s) B 1322. RNS 1320 may support one ormore cells. RNS 1320 may also include one or more RNC 1321/Node B 1322pairs or alternatively a single RNC 1321 may manage multiple Nodes B1322. RNS 1320 is responsible for communicating with Mobile Station 1301in its geographically defined area. RNC 1321 is responsible forcontrolling the Node(s) B 1322 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1321 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1301's access to the Core Network (CN) 1340.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1330 is aradio access network that provides wireless data communications forMobile Station 1301 and User Equipment 1302. E-UTRAN 1330 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1330 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1331 and E-UTRAN Node B (eNB) 1332. E-UTRAN 1330 may contain oneor more eNBs. User Equipment 1302 may be any user device capable ofconnecting to E-UTRAN 1330 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1330. The improvedperformance of the E-UTRAN 1330 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 9 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1301 may communicate with any or all of BSS1310, RNS 1320, or E-UTRAN 1330. In a illustrative system, each of BSS1310, RNS 1320, and E-UTRAN 1330 may provide Mobile Station 1301 withaccess to Core Network 1340. The Core Network 1340 may include of aseries of devices that route data and communications between end users.Core Network 1340 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1341 is part ofCore Network 1340, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1360 and Gateway MSCServer 1361 in order to facilitate Core Network 1340 resource control inthe CS domain. Functions of CS-MGW 1341 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1340 mayreceive connections to Mobile Station 1301 through BSS 1310, RNS 1320 orboth.

Serving GPRS Support Node (SGSN) 1342 stores subscriber data regardingMobile Station 1301 in order to facilitate network functionality. SGSN1342 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1342 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1344 address for each GGSN where an active PDPexists. GGSN 1344 may implement a location register function to storesubscriber data it receives from SGSN 1342 such as subscription orlocation information.

Serving Gateway (S-GW) 1343 is an interface which provides connectivitybetween E-UTRAN 1330 and Core Network 1340. Functions of S-GW 1343include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1350, and mobility anchoring forinter-network mobility. PCRF 1350 uses information gathered from S-GW1343, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1345 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1363 is a database for user information,and stores subscription data regarding Mobile Station 1301 or UserEquipment 1302 for handling calls or data sessions. Networks may containone HSS 1363 or more if additional resources are required. Exemplarydata stored by HSS 1363 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1363 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1360 provides user location functionality. WhenMobile Station 1301 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1360, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1301 registration orprocedures for handover of Mobile Station 1301 to a different section ofthe Core Network 1340. GMSC Server 1361 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1362 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1301. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1301 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1362, preventing its use on the network. Mobility ManagementEntity (MME) 1364 is a control node which may track Mobile Station 1301or User Equipment 1302 if the devices are idle. Additional functionalitymay include the ability of MME 1364 to contact an idle Mobile Station1301 or User Equipment 1302 if retransmission of a previous session isrequired.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention.Where the definition of terms departs from the commonly used meaning ofthe term, applicant intends to utilize the definitions provided herein,unless specifically indicated. The singular forms “a”, “an” and “the”are intended to include the plural forms as well, unless the contextclearly indicates otherwise. It will be understood that, although theterms first, second, etc. may be used to describe various elements,these elements should not be limited by these terms. These terms areonly used to distinguish one element from another. The term “and/or”includes any, and all, combinations of one or more of the associatedlisted items. The phrases “coupled to” and “coupled with” contemplatesdirect or indirect coupling.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements.

1. A method comprising: receiving in a radio network a request totransmit a message from a first device through a cellular network to asecond device, the request including a machine identity for the firstdevice and not including any QoS parameters; submitting a query to adatabase in a core network that correlates the machine identity with anassociated QoS parameter; determining the associated QoS parameterassociated with the first device based on the machine identity;assigning an assigned priority to the message, the assigned priorityselected from at least a first priority and a second lower prioritybased on the associated QoS parameter; and assigning the message to anassigned input queue in the radio network based on the assignedpriority, the assigned input queue selected from among a first inputqueue having a first associated delay into which a set of first prioritymessages are assigned and a second input queue having a secondassociated delay into which a set of second priority messages areassigned.
 2. The method of claim 1 wherein the associated QoS parameteris latency.
 3. The method of claim 2 wherein the first associated delayis shorter than the second associated delay.
 4. The method of claim 1further comprising holding the message in the assigned input queue untilall messages of higher priority have been transmitted.
 5. The method ofclaim 4 wherein first priority messages have low latency and secondpriority messages have higher latency.
 6. The method of claim 1 whereinthe first input queue and the second input queue are located in a eNodeB access point.
 7. A system comprising: a radio network; a core networkconnected to the radio network; a node in a radio network that receivesa request to transmit a message from a first device, the requestincluding a machine identity for the first device and not including anyQoS parameters; a subsystem that determines the machine identity for thefirst device; a storage medium in the core network; a database stored inthe storage medium that stores information associating the machineidentity with an associated QoS parameter; a subsystem in the corenetwork that determines the associated QoS parameter for the firstdevice based on the machine identity; a subsystem in the core networkthat assigns an assigned priority for the message based on theassociated QoS parameter, the assigned priority selected from among afirst priority and a second lower priority; a subsystem that assigns themessage to an assigned input queue in the radio network based on theassigned priority, the assigned input queue selected from among a firstinput queue having a first associated delay into which a first set ofassigned messages having the first priority are assigned and a secondinput queue having a second associated delay into which a second set ofassigned messages having the second lower priority are assigned.
 8. Thesystem of claim 7 wherein the associated QoS parameter is latency. 9.The system of claim 8 wherein the first input queue has a delay that isshorter than the delay of the second input queue.
 10. The system ofclaim 7 further comprising a transmitter that transmits a first set ofmessages in the first input queue, before transmitting a second set ofmessages in the second input queue.
 11. The system of claim 7 whereinthe first set of assigned messages in the first input queue have lowlatency and second set of assigned messages in the second input queuehave higher latency.
 12. The system of claim 7 wherein the first inputqueue and the second input queue are located in an eNode B access point.13. (canceled)
 14. (canceled)
 15. (canceled)
 16. (canceled) 17.(canceled)
 18. (canceled)
 19. (canceled)
 20. (canceled)